fix: proper field inversion for bigints#4802
Merged
TomAFrench merged 2 commits intomasterfrom Apr 15, 2024
Merged
Conversation
Loading
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Problem*
Resolves #4578. The fix for issue #4530 has also being merged back so I also activate the related test case.
Summary*
Field inversion for bigints had a typo.
Additional Context
I did not consider biguint256 since it was decided not to merge the PR.
Documentation*
Check one:
PR Checklist*
cargo fmton default settings.